Move round feature enablement - #8155

Codecov Report

❌ Patch coverage is 39.83740% with 148 lines in your changes missing coverage. Please review.
✅ Project coverage is 76.59%. Comparing base (f20b55b) to head (853e127).

@@            Coverage Diff             @@
##             main    #8155      +/-   ##
==========================================
- Coverage   76.94%   76.59%   -0.35%     
==========================================
  Files         458      459       +1     
  Lines       24418    24541     +123     
  Branches     6495     6525      +30     
==========================================
+ Hits        18788    18798      +10     
- Misses       5630     5743     +113     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

I had to check in a new package-lock.json to get npm ci to run in the , so something is off, but I've merged main and updated package-lock.json to match

Still need to double check, but with the new product tiers it is possible for a customer to buy a license for both hub and edge to unlock the full feature set. So we need to handle such license types.

I propose we allow the type to be a , separated list of tier types. This will require a slightly different approach for enabling features - a feature in hub & edge shouldn't get enabled twice because the license enables both.

I suggest we have a codified version of the tickbox table that maps feature to tiers (or tiers to features... not such which way around makes the most sense...)

const tierFeature = {
 featureName: { hub: true, edge: true, enterprise: true },
 ...
}

And then a utility function isFeatureEnabledForTier(string) => boolean - which either handles the comma array of tier types, or gets called multiple times and the result aggregated by the caller.

Can't that just be the enterprise license that we need to keep to ensure we test everything?

There is also the stuff about maybe including the cert nodes tokens in the license and the new feature listed about access to different BluePrint libraries (that we have not done any planing/design for yet)

With the new packaging, we are back to needing to providing separate limits on hosted/remote - the license asks for a combined limit. I'll work on the updates needed for that now.

I have pushed some updates:

1. fixed up the license version checks
2. added a remoteInstances feature flag (defaults to true, if the license is hub only, gets togged to false)
3. a number of front-end feature flag checks to disable remote instance UX as needed
4. centralised the overage check logic - a hub only license will have a limit of 0 remote instances; but we allow overages for licensed platforms. We don't want to allow overage for hub only on remote instances - so added that logic here.